PC Direct 1995 May

home *** CD-ROM | disk | FTP | other *** search

/ PC Direct 1995 May / PC Direct CD-ROM (May 1995).ISO / ipe / smr43e / disk1 / readme.txt < prev next >

Wrap

Text File | 1994-08-05 | 30.9 KB | 780 lines

McAfee BrightWorks v1.2 8/05/94 READ ME ***************************************************** This README.TXT file contains information on LAN Inventory 3.1.3, the integrated BrightWorks product, and SiteMeter 4.3. Print out the QUICKST.WRI for information on how to get started. (This in the installed directory.) ****************New and Improved in Brightworks v1.2****************** METERING - Agentless Windows and OS/2 metering are now supported. USAGE - Peak usage reporting is now available to network users running Usage.exe. CONSOLE - The number entries of unidentified software transferred to the PC software list is now dynamically updated. ****************New and Improved in Brightworks v1.1******************* INVENTORY - Manually added information to components is retained after audit. METERING - Netware 4.0 support with bindery emulation. - Netshld.NLM, Sitemetr.NLM and Smrproxy.NLM compatibility - Peaks will be retained on the usage console. ************************************* 1. Technical Specifications ************************************* 1.1.1 NetWare 3.11 - specific requirements The following modules are required: -LSLENH.NLM v1.01 or higher -PATCHMAN.NLM v2.3 or higher -MSM.NLM v2.2 or higher -A"TSM.NLM" module that corresponds to your particular topology ETHERTSM.NLM Ethernet TOKENTSM.NLM Token Ring etc... -The Latest LAN drivers (*.LAN) -CLIB.NLM v3.12f or higher These files are available on Compuserve in the following locations: CLIB.NLM Go NOVLIB Library 4 LIBUP2.exe All others Go NOVFILES LANDR3.exe Both files are self-extracting executables. Expand them into your SYS:SYSTEM directory to replace your old versions(Make sure the old versions are not marked "Read Only"). Then add the line Load LSLENH prior to the statement loading your LAN driver in AUTOEXEC.NCF. Finally down the server and restart it. 1.1.2 NetWare 3.12 Specific Requirements The only new file required is: - CLIB.NLM V3.12f or higher This new module is available on Compuserve Forum: Go Novlib Section: Library 4 File: LIBUP2.exe The file is a self-extracting executable. After expanding, copy CLIB.NLM into the SYS:SYSTEM directory. Down the server and restart it. 1.1.3 NetWare 4.x Specific Requirements No new modules are needed. The only requirements are that NetWare 4.01 or later is running. (250 user or lower) and that bindery emulation is active. 1.2 Compatible with NetWare 2.2, 3.xx and 4.x. 1.3 The BrightWorks 1.xx console PC must have MS/PC DOS 3.3 (or later), a *minimum* of 4Mb installed RAM, and be capable of running Microsoft Windows 3.1x in Enhanced Mode. BrightWorks 1.1 also requires a mouse. Please Note: The BrightWorks console (and install program) only supports Windows 3.1x in Enhanced Mode. Windows 3.0x is not supported. 1.4 A *minimum* of 15mb of file server disk space is required to install the BrightWorks 1.2 program files and databases. Additional space is required for upgrading from previous versions of LAN Inventory or SiteMeter. An additional .5 Mb of space needs to be available on the System volume for the files that are installed in the System directory. 1.5 If you are using DOS v6.0 please use NETX v3.32. 1.6 If you are using server based Btrieve, you must use BREQUEST ver. 6.1 or higher. Brequest.exe can be found on the first install diskette. Copy brequest.exe to your public directory. 1.7 McAfee BrightWorks is compatible with Novell's NMS. Please refer to Appendix "F" of the User's Guide to find out more about Smart Launching BrightWorks from within NMS. ************************************* 2. Installation Requirements ************************************* 1. A drive needs to be mapped to the SYS volume for the destination server upon which the software is being installed. Note: The install will only display the servers that meet this requirement. 2. If you plan on upgrading your installed copy of LAN Inventory, please consider the following before proceeding: (a) Disk space requirements: make sure that you have enough available space on your network drive. A pretty good rule-of-thumb is that you will require at least 4 times the space that is currently being occupied by your copy of LAN Inventory. Use the VOLINFO, CHKDIR, or CHKVOL commands to determine your available space. (b) Time: The routine to convert your LAN Inventory data can take quite a bit of time to complete. Depending on some variables, the conversion routine can require from 1 to 6 hours -- possibly more, if your existing LAN Inventory 2.xx or 3.0x directory is greater than 9 Mb in size. Given this, you may want to dedicate a PC to the task of converting from your existing LAN Inventory installation. (c) Workstation Environmental Precautions: IF YOU ARE NOT USING v1.13 of VIPX.386, MAKE sure that IPX/SPX (or IPXODI) is not loaded into high memory BEFORE you begin the UPGRADE. (d) PC Software List: BrightWorks (formerly Fusion 1.0) 1.2 includes an updated PC Software list that provides improved identification of installed applications on your network. During the upgrade installation you have the option of using the new list, or preserving your old list. McAfee "HIGHLY" recommends using the new list for the most complete and accurate identification of software packages. ************************************* 3. BrightWorks 1.2 Installation ************************************* 3.1 For complete details about the Installation please refer to the to Chapter 2 in the User's Manual. 3.2 If you are upgrading from Fusion 1.0, LAN Automatic Inventory 3.1, Site Meter 4.1 or Brightworks 1.0.1 please choose, from the upgrade options, to upgrade from Fusion 1.0, Brightworks 1.0.1, LAI 3.1 or SiteMeter 4.1. You want to install this release into the same directory that currently exists. The install will ask you if you want to install into the same directory (Say Yes) and then it will ask you if you want to overwrite the existing Data. If you DO NOT want your existing data to be overwritten, say NO to this prompt. Note: Once the Install is completed, You MUST manually load the Sitemetr.nlm or Vap and the Smrproxy.nlm on the file server console. ************************************* 4. Install Error Messages ************************************* 4.1 "Internal Error: -999" This indicates that you are running install in Windows v3.0. The NetWare function to provide the version information does not work properly with v3.0 Windows. [Solution: install BrightWorks from a machine that is capable of running Windows 3.1x in Enhanced Mode. (See next note)] Please Note: The BrightWorks 1.1 console (and install program) only supports Windows 3.1x in Enhanced Mode. Windows 3.0x and Windows for Workgroups are not supported. 4.2 "ValidateIPXNETXVersion Error: 254" This error may be due to one of the following: (a) You are running a version of IPX/SPX less than v3.1. [Solution: upgrade your IPX/SPX to v3.1. The OBJ file for IPX 3.1.10 can be found on CompuServe --in the Novell Libraries: GO NOVLIB; LIBrary 5; filename (as of this writing) DOSUP9.ZIP] Please Note: if you are using the ODI drivers, v1.20 or 2.10 are recommended over v2.00. (b) You are not logged in as a supervisor (or equivalent), and the following has occurred: 1) Run Windows 2) Exited out of Windows 3) And have run Windows again. [Solution: Issue (b) is due to a bug in the VIPX.386 drivers version 1.11 and earlier. This has been fixed in version 1.13, which is available on CompuServe -- in the Novell Libraries: GO NOVLIB; LIBrary 5; filename (as of this writing) WINUP9.ZIP] (c) IPX/SPX (or IPXODI) is loaded high. Solution: UPDATE to v1.13 of VIPX.386 or take IPX/SPX (or IPXODI)out of upper memory. (d) This error can also occur on workstations that have EMSNETX loaded. [Solution: either reboot the workstation, and load a conventional NETX shell, or run the install from a workstation that loads a conventional NETX.] 4.3 "Btrieve Error 90": A Btrieve Error 90 is a "Redirection Device Table Full" error. If you're getting this message, it usually means that you have an older version of BREQUEST.EXE in your search path, and *it* is loading instead of BREQUEST v6.10. 4.4 How to revert to using "local Btrieve": If you would like to disable the Btrieve Requester for Windows and have BrightWorks access client-based Btrieve instead, follow these steps: - From a DOS prompt -- outside of Windows, and in the BrightWorks 1.2 directory -- execute USEBTR.BAT. This batch file will "enable" the client-based version of WBTRCALL.DLL by first renaming the server-based version of WBTRCALL.DLL to WBTRCALL.BRQ, then rename the client-based version to WBTRCALL.DLL. ******************************************** 5. Helpful Hints for Inventory ******************************************** 5.1 NetWare Global Naming Service If you are using the NetWare Naming Service, place EQUIP in the PROFILE Login script. EQUIP will not run from the DOMAIN Login script. 5.2. To audit multiple sites, the files that are required from the remote sites are: WEQLOG.DAT WEQTRN.DAT WSYSFLOG.DAT WSYSFTRN.DAT WTRSOFTT.DAT These files are commonly referred to as the "Transaction Files". Please note that Software Distribution is only available to nodes that reside in the Local Site. PCs that are in your "transaction directory" cannot receive files via Software Distribution. 5.3. Creation of Collector's Diskette MUST be done from the BrightWorks console using the Create Collector Diskette command. DO NOT copy the information from one diskette to another via DOS copy commands. 5.4. If you would like to use Microsoft's screen savers during an Audit please follow these steps: 1. In Windows, go under MAIN, Control Panel, 386 Enhanced and increase Windows in Background to 500. 2. Begin to run your Audit or schedule an Audit to run. 3. Go back into MAIN, Control Panel, Desktop and invoke the screen saver by clicking on Test. Note: This procedure only needs to be followed for Microsoft screen savers. If you experience any problems with any other type of screen savers, please contact Technical Support. 5.5. If your Windows is set up to use the 1024x768 Large Font driver, headers will be shown misaligned with the respective columns. 5.6. If you are using VLMs on the workstation where you run BrightWorks, Inventory will not detect serial numbers on file servers. Inventory will also not be able to detect CPU and RAM info for 2.x file servers when BrightWorks is run from a workstation that uses the VLMs. 5.7. If you are loading BREQUEST or BTRIEVE from a Login script in order to run EQUIP you may experience problems with BREQUEST or BTRIEVE hanging if you are using LOGIN.EXE version 4.xx. There are two workarounds for this problem: A. In a mixed environment of NetWare 2.xx, 3.xx and 4.xx where the file server you are logging into is NOT a NetWare 4.xx file server you may add a PREFERRED SERVER= statement to your SHELL.CFG or NET.CFG file. This will prevent your workstations from invoking a copy of LOGIN.EXE v4.xx and will thus avoid the potential BTRIEVE or BREQUEST hang. B. If your environment is all NetWare 4.xx or if you are in a mixed environment but you are attempting to log into a NetWare 4.xx server you should load BREQUEST or BTRIEVE and execute EQUIP from a batch file. This batch file can be called from within the Login script by using Novell's External Execution switch (#). The Login script should resemble the following: MAP F:=VOL1:APPS\BRIGHTWORKS ; map F: to the BrightWorks directory DRIVE F: ; change to F: #COMMAND /C DOEQUIP.BAT ; shell out and call DOEQUIP.BAT The batch file should resemble the following: (it should be created in the BrightWorks directory) ENDBTRV ;unload Brequest (or Btrieve) if loaded BREQUEST /D:17000 ;load Brequest with parameters rem If you prefer to load BTRIEVE.EXE instead, use rem BTRIEVE /P:3072 /F:22 /T:BTR.TRN /E EQUIP /H /Y /S /SHOW ;inventory hw, sw and system files w/echo ENDBTRV ;unload Brequest (or Btrieve) 5.8. Users may wish to consolidate inventory data from remote sites and incorporate this information in their local databases. This may be accomplished by either consolidating transaction information or by consolidating baseline information. Instructions for both methods follow: A. Consolidating Transaction Information: Copy the five Transaction files (weqtrn.dat, wtrsoftt.dat, weqlog.dat, wsysftrn.dat, wsysflog.dat) from the remote site to a directory you have created for them on your local network. If you are consolidating more than one site you will need to create a directory for each of these sites. Then from within the BrightWorks (or LAN Inventory) console define that directory (or directories) as a Site from the Define Sites screen. Include the Site(s) in your Scope of Audit and perform the Audit. The Audit will incorporate the Transaction information into your local Baseline, where the data can be edited, viewed and reported on from within the BrightWorks (or LAN Inventory) console. B. Consolidating Baseline Information: In order to get file server information from a local site merged with your local Baseline you must consolidate Baseline information. If you want to include any edits made to inventory you must also use this method when consolidating information from remote sites. Export the baseline using the copy of BrightWorks (or LAN Inventory) at the remote site. The Export Baseline command is found under the Administration/Inventory menu. Once you have exported the baseline data you may then import it into your local copy of BrightWorks (or LAN Inventory) using the Import Baseline command under the Administration/Inventory menu. Once you have imported the data there is no need to do a subsequent Audit since the Import process will merge the remote Baseline information into your local Baseline as long as the site names for the data are unique. The data can now be edited, viewed and reported on from within the local BrightWorks (or LAN Inventory) console. 5.9 Due to a limitation of Microsoft's Common Dialogs, you may encounter a message "The number of files retrieved is less than the number specified..." when adding files to a Fileset. The message will return what the last file retrieved was,and you can then go in and specify additional files. 5.10 NIC Cards with multiple protocols bound to them (as possible with ODI drivers) may return incorrect NIC card information in the inventory. 5.11 Supervisor or equivalent rights are not required to obtain access to the LAN Inventory console. However, to run an Audit on a file server or to obtain access to the Sitemeter or BrightWorks console, Supervisor or equivalent rights are required. 5.12 Bworks.ini The Bworks.ini file is created in the Windows directory of the PC that runs BrightWorks. The sections that may be added are: [Downgrade] Module=Inventory The next time that BrightWorks is launched on that PC only the inventory module of BrightWorks will be available and visible to that user. [Downgrade] Module=Metering The next time that BrightWorks is launched on that PC only the metering module of BrightWorks will be available and visible to that user. To allow the user to use the full BrightWorks product again simply remove the [Downgrade] section from the Bworks.ini file. Another section may be added to the BWORKS.INI that will allow you to disable the Set Policy and Security Scan Interval commands for the metering module of BrightWorks. Add the following to disable these commands: [Restrictions] EditLevel=4 The final section that may be added to the BWORKS.INI will allow you to show the FULLNAME for the Current and Queued User windows instead of the USERNAME. This change applies globally to all windows of this type. Add the following commands to enable the FULLNAME display feature: [Current User Information] Fullname=Yes Note: To change the display back to the USERNAME edit the Bworks.ini to reflect Fullname=No. 5.13 The NetWare Full Name call be passed to EQUIP.EXE in the Login script. Use the following line in the System Login Script: #EQUIP /s /h /y /u="%FULL_NAME" This can only be done in the Login script. If the variable is used at the command line the node name will be %FULL_NAME. If the full name is not defined in Syscon the node will appear in Inventory as "Unknown" since that is the value NetWare returns for %FULL_NAME when no full name is defined. The node names in inventory do not update on subsequent audits. Therefore if you do not use the /u switch the first time equip is run on a PC and then use the /u switch the next time Equip is run the name will not be updated to the new value. The Inventory name will also not change to a new value if /u is used with one name and is then used later with a different name. Inventory will always retain the first name used with Equip. 5.14 All users must have the RCWFE rights in order to execute EQUIP.EXE. This is because Equip creates pre-image files and they are deleted once Equip has run. If the user does not have sufficient rights the pre-image files will not be able to deleted. This could cause some date integrity problems with the data that Equip collects. ****************************************************************** 6.0 Sitemeter At A Glance ****************************************************************** 6.1 Upgrading If any of your older SiteLock files have been virus protected, remove them from the authorized list before upgrading to Sitemeter 4.3. Remember to change any RO (ReadOnly) flagged files to RW (ReadWrite) before beginning the install procedure. Also, turn the 'Run Authorized Files' flag ON if it is OFF. If you have chosen to continue with our Wrapping Technology, the Sitemeter NLM can be made backwards compatible by loading the NLM with the -o flag. Example: :LOAD SITEMETR -O Sitemeter will log in as the user SiteLock and be compatible with your wrapped files. ***************************************************************** 7. Helpful Hints for Metering and Sreports ***************************************************************** 7.1 To Determine What Files To Meter If you are having trouble metering an application, and you have defined the application's .EXE file as the file to meter, the one you have chosen may not be the correct one. By using the MONITOR console utility from your file server, (or from a workstation using RCONSOLE), you can determine what files are being opened, and which files stay open. Enter Connection Information, choose a user and have that user open the troublesome application. MONITOR displays all files that are opened and closed. Meter the file that stays open throughout the user's whole session. DLLs, BINs, OVLs and BAT files can be metered by editing the sitemetr.ext file found in \system\sitemetr.ext 7.2 Setting the Security Scan Interval This setting tells the NLMs to scan the network at a set interval for those users who do not have SWATCHER loaded on their workstations. If this interval is set to any number other that zero, and users do not have SWATCHER loaded, these users will be disconnected from the network within 30 seconds of the scan. This includes any Macintoshes that are on the network. If you wish to use this feature, and have users that are to be exempt from the network disconnect, add those users to the Security Exceptions list from the Security menu. 7.3 Using Virus Protection Be sure to select the files for File Authorization before setting the option to *NOT* allow Authorized Files to be run. Include LOGIN.EXE, and COMMAND.COM at the very least. To run Windows, also authorize WIN.COM, WIN386.EXE, KRNL386.EXE, GDI.EXE, USER.EXE, PROGMAN.EXE, and SITEMETR.EXE. **CAUTION** If you set up Sitemeter so that Authorized Files are *NOT* allowed to run and no files have been registered for File Authorization, you will not be able to run ANY files on your network. If you find yourself in this situation, unload the NLMs from the server console and reload. For NetWare 286, rename the VAP, down the server and reboot or run the Sitemetr.exe from a local drive. 7.4 Upgrading Your Novell Software This product was not regression tested with releases earlier than NetWare 2.2. Swatcher does not support Suite Metering on NetWare 386. Also, we recommend you upgrade to the latest supportable shells and drivers released from Novell. 7.5 NetWare FCONSOLE/MONITOR Do not use FCONSOLE or MONITOR to disconnect the users SITEMETR and SMRPROXY. If you disconnect these users, software metering and file authorization will be disabled. In addition, an "Abend: Invalid Server Number" error may occur and the file server will lock up. If this occurs, reboot the file server. NOTE: When running SITEMETR.VAP, there will be TWO users logged in called SITEMETR. Do not disconnect either of these two users. 7.6 Network Security Scans on Multi-Server Networks The network security scan, which ensures that all users have Swatcher loaded, will scan anyone either logged in to or ATTACHED to a given server. One server cannot expel a user from another server unless that user is attached to both servers in some way. This includes any CAPTUREs to print queues, since a capture involves attaching to another server as GUEST, a user subject to the security scan. To avoid these difficulties, GUEST may be included on the Security Exceptions List (in the Security menu) or Swatcher can be loaded on workstations using GUEST as a Login. 7.7 Disabling Local File Execution If local file execution is disabled, attempting to run Windows from a local drive will evoke a message that says "Invalid COMMAND.COM, system halted". Also, COMMAND.COM may not be found if DOS needs to refresh itself in memory after running a sizable application, or even during normal use. To avoid these problems, the environment variable COMSPEC must be set to a network copy of COMMAND.COM. In the Login script, add the line: DOS set COMSPEC="[path]" where [path] is the complete pathname of COMMAND.COM (for example, f:\dos\command.com). A similar problem may occur with EMM386.EXE while starting Windows. To solve this, use the undocumented /Y switch in CONFIG.SYS to point to a copy of EMM386.EXE on the network. For example: DEVICE=EMM386.EXE RAM /Y=F:\DOS\V5.00\EMM386.EXE 7.8 If a lockset stops working Occasionally a lockset which had been behaving properly may stop working correctly. For example, when a user exits a metered application, that user is not removed from the list of current users. If such behavior should surface, a very effective solution is to simply delete the lockset and immediately readd it. Keep in mind that any information about current and queued users of the metered application will be lost upon deletion of the lockset. 7.9 Using Swatcher.com You must load Swatcher AFTER loading IPX and NETx shells. This should be done from the AUTOEXEC.BAT file. 7.10 Using Local Btrieve with Sreports If you are using local Btrieve instead of Brequest with Sreports it is necessary to place the following lines in your win.ini: [Btrieve] options=/p:3072 /f:22 /t:btr.trn /e If these lines are not in the win.ini you will receive the error "Page size error, Btrieve error code 24". 7.11 If you experience a GPF in UNIDRV.dll while using Sreports from the SiteMeter/BrightWorks console and you are using v3.1.x of UNIDRV.dll , downgrade your Universal Driver (UNIDRV.dll) from your original Windows diskette or makesure you close all open report windows prior to exiting Sreports. To find out what version of the Universal Driver that you are using follow these steps: 1. From your Windows Main group launch Control Panel 2. Select Printers 3. Go under Setup for your Default Printer 4. Click on About 7.12 Do not allow the Sitedata file to become more than 2.6mb in size. Allowing this file to reach this size may cause some problems during an export. Rename your Sitedata file so a new one will be created or Purge Usage Information under Adminstration, Monitoring. 7.13 Full Name under NetWare 4.0 Unlike NetWare versions before it, NetWare 4.0 does not store the full Name of a user. This has two effects on SiteMeter: A. In the User Information box (accessed by viewing current or queued users of a lockset, the "Fulle Name:" will be blank. B. The Bworks.ini statements [Current User Information} Fullname=Yes will have no effect. (See Section 5.12 for further information. ***************************************************************** 8. Using Sitemeter with Microsoft Windows ***************************************************************** To meter Windows applications while loading Swatcher, Sitemeter depends on a different utility run from Windows, SWINAPP.EXE (short for Swatcher WINDOWS APPLICATION). SWINAPP is also loaded from the win.ini file. Users will still need to load the Swatcher TSR when they attach to the network. If you do not load Swatcher before running Windows and SWINAPP is loaded from the Win.ini file, Windows will exit you back out to the DOS prompt. The batch file Smruser.bat, when included in the system Login script, will automatically alter each user's WIN.INI file for you. Here are some notes on manually editing WIN.INI if you should choose to do so. This file exists in your program directory. Create (or edit) the LOAD statement under the [Windows] section header within the WIN.INI file, so Swinapp will be loaded properly. 1) SWINAPP.EXE (TSR) must be in the Load statement in order to meter Windows applications. 2) Windows only recognizes the first LOAD statement it finds, so all files to be loaded must be included in one LOAD statement. 3) Each filename should be separated with a space. For example: The Swatcher (TSR) method: load=f:\public\SWINAPP.EXE NWPOPUP.EXE CLOCK.EXE ********CRITICAL NOTE!!!!******* When using Sitemeter and Microsoft Windows with NetWare versions 2.2 and 3.1.x, the group "EVERYONE" must have read (R) and file scan (F) rights to SYS:PUBLIC in order to access SWINAPP.EXE. ************************************************************* 9. Known Problems With the Metering Portion of BrightWorks ************************************************************* 9.1 With NetWare 2.2 using the VAP, active user names sometimes appear twice in View application usage. 9.2 Opening a metered file through File, Properties will cause Sitemeter to incorrectly start metering that application. One workaround is to edit the PROGMAN.INI under [Restrictions] and add the following line: Editlevel=4. This will disallow anyone from editing the icon, but will allow it to be opened for reading. (This may occur with the TSR method only.) 9.3 Not using a full path when defining a Metered Application that will be an iconized DOS application on a Windows user's desktop may or may not meter. 9.4 Files flagged as Execute-Only can not be authorized for file integrity. 9.5 There is a known problem with locksets being released when using QEMM. The workaround for this problem is to remove the LoadHigh verb from the CONFIG.SYS: LH shell=c:\command.com /r or remove the shell statement from the CONFIG.SYS and add the following to the autoexec.bat: set comspec=c:command.com 9.6 The limit on Metered Applications on any file server is 500 files. There is a bug that will allow you to add more than 500 files to this list. If more than 500 files are added the product will stop metering. The workaround for this problem is to enter ONLY up to 500 files to the Metered Applications list. ******************************************************************************* User Feedback Department ******************************************************************************* Send written comments to: McAfee, Inc. 766 Shrewsbury Avenue Tinton Falls, N.J. 07724 Fax: (908) 576-8867 Or by Internet Customer_Service@brightwork.com Or by CompuServe Mail Box: 73500,1415 Forum: go BRIGHT Or call technical support at: (908) 530-9650 from 9:00 AM to 7:00 PM, Monday - Friday, Eastern Time *******************************************************************************